Feature-based flow control in remote computing environments

ABSTRACT

The disclosure provides an approach for print redirection in a remote computing environment. Embodiments include receiving, on a remote device, a request to perform a printing task using a printing device associated with a client device. Embodiments include determining, on the remote device, that data associated with the request to perform the printing task exceeds a size threshold. Embodiments include generating, on the remote device, a plurality of data slices based on the data, wherein each respective data slice of the plurality of data slices comprises a respective subset of the data that does not exceed the size threshold. Embodiments include transmitting, from the remote device to the client device, the plurality of data slices as separate transmissions in separate time intervals along with information that allows the data to be reconstructed from the plurality of data slices for performing the printing task on the client device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims benefit of and priority to InternationalApplication No. PCT/CN2021/137830, filed Dec. 14, 2021, which is herebyassigned to the assignee hereof and hereby expressly incorporated byreference herein in its entirety as if fully set forth below and for allapplicable purposes.

BACKGROUND

In a virtual desktop infrastructure (VDI) environment, a local clientdevice can access and display a remote virtual or physical desktop orremote application that is running on a remote device. For instance, avirtual desktop may be hosted on a central infrastructure known as aVDI, and may be rendered on a client device using a remote displayprotocol. At the client device, a user may interact with the virtualdesktop using peripheral devices (e.g., keyboard and mouse, pen, etc.)associated with the client device, and operating system (OS) eventsgenerated based on the user's inputs may be redirected from the clientdevice to the remote device on which the virtual desktop is actuallyrunning.

In some cases, a printing device (“printer”) associated with the clientdevice may be used to print data associated with the virtual desktop orother remote application on the remote device. In certain aspects, thevirtual desktop or remote application on the remote device may transmitsuch data to the client device for printing.

Transmitting the data to be printed from the remote device to the clientdevice may involve a substantial amount of network traffic, and mayresult in latency and poor performance for other aspects of the remotecomputing environment, such as redirection of other, potentiallyhigher-priority, data between the client device and the remote device.Transmitting the data promptly may serve only to congest the network andmay not result in the data being printed any faster, as printersgenerally take a significant amount of time to process a print requestand print the data. The congestion caused by transmitting potentiallylarge amounts of data for printing from the remote device to the clientdevice in a short amount of time may significantly reduce the ability ofa virtual desktop or other remotely-located application to function asintended during this time.

Accordingly, there is a need in the art for improved techniques forprint redirection between a virtual desktop or remote application on aremote device and a printer associated with a client device.

It should be noted that the information included in the Backgroundsection herein is simply meant to provide a reference for the discussionof certain embodiments in the Detailed Description. None of theinformation included in this Background should be considered as anadmission of prior art.

SUMMARY

A method of print redirection in a remote computing environment isprovided. The method includes: receiving, on a remote device that isremote from a client device, a request to perform a printing task usinga printing device associated with the client device; determining, on theremote device, that data associated with the request to perform theprinting task exceeds a size threshold; generating, on the remotedevice, a plurality of data slices based on the data, wherein eachrespective data slice of the plurality of data slices comprises arespective subset of the data that does not exceed the size threshold;and transmitting, from the remote device to the client device, theplurality of data slices as separate transmissions in separate timeintervals along with information that allows the data to bereconstructed from the plurality of data slices for performing theprinting task on the client device.

Further embodiments include a non-transitory computer-readable storagemedium storing instructions that, when executed by a computer system,cause the computer system to perform the method set forth above. Furtherembodiments include a computing system comprising at least one memoryand at least one processor configured to perform the method set forthabove.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a virtualized desktop infrastructuresystem in which one or more embodiments according to the presentdisclosure may be implemented.

FIG. 2 is an illustration of a prior art technique for print redirectionin a remote computing environment.

FIG. 3 is an illustration of an improved technique for print redirectionin a remote computing environment, according to embodiments of thepresent disclosure.

FIG. 4 depicts example operations related to print redirection in aremote computing environment.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in oneembodiment may be beneficially utilized on other embodiments withoutspecific recitation.

DETAILED DESCRIPTION

The present disclosure provides an approach for improved printredirection in a remote computing environment. In some cases, a printingdevice, which may be referred to as a printer, connected to a clientdevice may be used by an application (e.g., virtual desktop or otherapplication) located on a remote device to print data from the remotedevice. As such, data to be printed must be redirected from the remotedevice to the client device in order to send the requested print job tothe printer. A print job generally refers to a request to print certaindata. According to certain existing techniques, print redirection may beaccomplished through operating system (OS) event redirection, which isdescribed in more detail in U.S. patent application Ser. No. 16/444,840,the contents of which are incorporated by reference herein in theirentirety.

However, conventional techniques for print redirection in remotecomputing environments may involve the transmission of a substantialamount of data over a network in a short amount of time. Print jobs tendto involve large amounts of data, such as many megabytes (MB) per pageto be printed, and this data may be transmitted at a high rate, such asfour MB per second. As described in more detail below with respect toFIG. 2 , transmitting data for a print job at such a rate may congest oreven monopolize the network connection between the remote device and theclient device, thereby preventing other aspects of the remote computingenvironment from functioning properly. For instance, other types of datamay be of a higher priority than print jobs and/or may require prompttransfer in order to provide an intended function properly, such asredirection of mouse or keyboard input from the client device to avirtual desktop on the remote machine or transmission of a virtualdesktop screen from the remote device to the client device. The networkcongestion caused by transmitting print job data at a high rate maycause significant lag in these other aspects of the remote computingenvironment, thereby harming the functioning of the system with nodiscernible benefit (e.g., because the printer will still take a certainamount of time to process the print job and print the data, regardlessof how quickly the print job data is transmitted to the client device).

As such, due to the relatively low priority and non-time-sensitivenature of print jobs, embodiments of the present disclosure allow thetransmission of data related to print jobs over a network to berate-limited in order to reduce network congestion. For instance, inorder to achieve a particular transmission rate, certain embodimentsinclude splitting data related to a print job into a plurality ofslices, and transmitting these slices sequentially at fixed intervals.As described in more detail below with respect to FIG. 3 , each slicemay contain an amount of data that is less than or equal to a sizethreshold (e.g., 400 kilobytes (KB)), and one slice may be sent per timeinterval (e.g., one second) in order to achieve a particulartransmission rate (e.g., 400 KB per second).

In some embodiments, a protocol data unit (PDU) for the print job issplit into a plurality of slices that are separate PDUs. A PDU is asingle unit of information transmitted among peer entities of a computernetwork, and generally includes a PDU header with attributes of the PDU.For example, a slice may be a PDU with a PDU header includinginformation that allows the original full PDU of the print job to bereconstructed from the plurality of slices. In one example, the PDUheader of a slice includes an identifier associated with the print job(e.g., which is common to all of the slices generated from the printjob) and an ordering value that indicates what order to arrange theslices in for reconstruction of the original full PDU. For example, theordering values of the slices may be sequential numerical values thatindicate the order of the slices (e.g., 0, 1, 2, 3, etc.). In somecases, the final slice of the print job may include an ordering valuethat indicates that it is the final slice (e.g., a particular number orcharacter such as “f”) or a separate indicator (e.g., in addition to theordering value) that indicates that it is the final slice. In otherembodiments, the ordering value of a given slice indicates whether thegiven slice is the first slice, a middle slice, or the last slice of theprint job (e.g., if the slices are expected to be transmitted andreceived in order). For instance, an ordering value of “0” may indicatea first slice, “1” may indicate a middle slice, and “2” may indicate alast slice.

When a given slice is received on the client device, the PDU header ofthe slice is used to determine how the given slice is to be used toreconstruct the print job. For instance, if an identifier in the PDUheader of the given slice indicates that the given slice is the firstslice of the print job, then a new buffer is created on the clientdevice associated with the identifier of the print job indicated in thePDU header. Subsequently-received slices having the same identifier andvalues indicating that the slices are middle slices of the print job areadded to the buffer associated with the identifier. When a slice havingthe identifier is received with a value indicating that the slice is thefinal slice of the print job, the slice is added to the end of thebuffer, and a complete PDU for the print job is constructed on theclient device from the buffer. The complete PDU is then passed on (e.g.,to an event handler on the client device) to be processed by theprinter.

In some cases, the transmission rate limit for print jobs is set (e.g.,by a network administrator) via a user interface or through interactionwith application programming interface (API). For instance, anadministrator may set transmission rate limits for various types offeatures (e.g., print jobs, storage I/O operations, mouse/keyboardredirection, touch input redirection, virtual desktop screenredirection, and/or the like), and the rate limits may be enforced usingtechniques described herein. It is noted that while certain embodimentsare described with respect to print redirection, techniques describedherein for rate-limiting print redirection may also be used torate-limit other types of data that may be transmitted over a network,such as in a VDI environment.

Techniques for print redirection in remote computing environmentsdescribed herein improve upon conventional techniques for printredirection by avoiding the unnecessary network congestion caused bytransmitting large amounts of data associated with print jobs at a highrate over a network. Embodiments of the present disclosure allowtransmission of data related to print jobs to be rate-limited in orderto keep network resources consistently available for other types of datatransmission that may have a higher priority and/or that may be moretime-sensitive. For example, by preventing a network connection frombecoming temporarily monopolized by the transmission of large amounts ofprint job data at a high rate, embodiments of the present disclosureallow time-sensitive features such as user input redirection and virtualdesktop screen redirection to continue to function properly while printjob data is transmitted over the network.

FIG. 1 depicts a block diagram of a virtualized desktop infrastructure(VDI) system 100 in which one or more embodiments according to thepresent disclosure may be implemented. VDI system 100 comprises at leastone client device 104 and a data center 102, connected by a network 146.Network 146 may be, for example, a direct link, a local area network(LAN), a wide area network (WAN) such as the Internet, another type ofnetwork, or a combination of these.

Client device 104 is a physical device, such as a general purposedesktop computer or mobile computer. A mobile computer may be, forexample, a laptop, a mobile phone, or a tablet computer. Client device104 includes VDI client 134, OS 132, and transport client plugin 136. Incertain embodiments, VDI client 134 and transport client plugin 136 runon top of OS 132. OS 132 may be a standard, commodity operating system.

VDI client 134 is a user-side interface of a virtualized desktop runningon one of virtual machines (VMs) 120. Though certain aspects aredescribed herein with respect to a virtual desktop running on a VM, thetechniques may similarly be used for a virtual desktop or applicationrunning on other types of VCIs, such as containers, or on physicalcomputing devices. As used herein, a “virtualized desktop” or “remotedesktop” is a desktop running on, for example, one of VMs 120 that isdisplayed remotely on client device 104, as though the remote desktopwere running on client device 104. By opening VDI client 134, a user ofclient device 104 accesses, through network 146, a remote desktoprunning in remote data center 102, from any location, using clientdevice 104. Frames of the remote desktop running on VM 120 aretransmitted to VDI client 134 using a desktop delivery protocol such asVMware® Blast™, or Microsoft® Remote Desktop Protocol (RDP)™.

After transmission, the frames are displayed on client device 104 forinteraction by the user. Client device 104 sends user inputs to VM 120for processing on VM 120 of data center 102, taking processing load offclient device 104. Such centralized and automated management of remotedesktops provides increased control and cost savings. VDI client 134 maybe, for example, VMware® View™, or a special purpose thin client such asthose available from Dell, HP, NEC, Sun Microsystems, Wyse, and others.

As the user interacts with the virtual desktop, such as using a mouseand keyboard and/or other peripheral devices, the user input events maybe redirected by VDI client 134 to VDI agent 124. A printing device 140is connected to client device 104, and may be used to print data from VM120, such as by the virtual desktop and/or one or more applications 123.

Transport client plugin 136 generally comprises an application thatperforms operations related to transmission and reception of PDUs, suchas for print jobs, user input redirection, and other types of eventredirection between client device 104 and VMs 120. For example, avirtual channel may be established between transport client plugin 136and transport agent plugin 126 on VM 120. A virtual channel is a logicalcommunication resource between two endpoints that is allocatedparticular communication resources from one or more physical networkinterfaces associated with the two endpoints, and allows forcommunication between the two endpoints. In one embodiment, transportclient plugin 136 is a plugin installed in client device 104, such aswithin VDI client 134 or is a separate application from VDI client 134.

It is noted that while transport client plugin 136 is depictedseparately from VDI client 134, transport client plugin 136 mayalternatively be included within VDI client 134. Furthermore, while notshown, client device 104 may further comprise a bridge component thatacts as an intermediary between transport agent plugin 126 and transportclient plugin 136.

Data center 102 includes host(s) 105, a virtualization manager 130, agateway 138, a management network 128, and a data network 118. Althoughthe management and data network are shown as separate physical networks,it is also possible in some implementations to logically isolate themanagement network from the data network using different VLANidentifiers. Each of hosts 105 may be constructed on a server gradehardware platform 106, such as an x86 architecture platform. Forexample, hosts 105 may be geographically co-located servers on the samerack.

Host 105 is configured to provide a virtualization layer, also referredto as a hypervisor 116, that abstracts processor, memory, storage, andnetworking resources of hardware platform 106 into multiple VMs 120 ₁ to120 _(N) (collectively referred to as VMs 120 and individually referredto as VM 120) that run concurrently on the same host. Hypervisor 116 mayrun on top of the operating system in host 105. In some embodiments,hypervisor 116 can be installed as system level software directly onhardware platform 106 of host 105 (often referred to as “bare metal”installation) and be conceptually interposed between the physicalhardware and the guest operating systems executing in the virtualmachines. In some implementations, the hypervisor may comprise systemlevel software as well as a “Domain 0” or “Root Partition” virtualmachine, which is a privileged machine that has access to the physicalhardware resources of the host. In this implementation, one or more of avirtual switch, virtual tunnel endpoint (VTEP), etc., along withhardware drivers, may reside in the privileged virtual machine. Althoughthe disclosure is described with reference to VMs, the teachings hereinalso apply to other types of virtual computing instances (VCIs), such ascontainers, Docker containers, data compute nodes, isolated user spaceinstances, namespace containers, and the like. One example of ahypervisor 116 that may be used is a VMware ESXi™ hypervisor provided aspart of the VMware vSphere® solution made commercially available fromVMware, Inc. of Palo Alto, Calif.

Each VM 120 includes a guest OS 122, one or more applications 123, a VDIagent 124, and transport agent plugin 126. Application(s) 123, VDI agent124, and block device agent 126 run on top of guest OS 122. Guest OS 122may be a standard, commodity operating system. An application 123 may beany software program, such as a word processing program.

VDI agent 124 is a desktop virtualization program that connects to VDIclient 134 of client device 104, through network 146. The connectionbetween VDI agent 124 and VDI client 134 may be authenticated, such asthrough a username and password combination pertaining to client device104 or to a user of client device 104. VDI agent 124 transmits, to VDIclient 134, image frames of the remote desktop running on VM 120 thatcontains VDI agent 124. An image frame includes information onappearance of the remote desktop running on VM 120, and that informationincludes pixel color and location information. In addition to an imageframe, VDI agent 124 may also transmit metadata of that frame to VDIclient 134. The metadata may include x and y coordinate locations of amouse cursor, x and y coordinates and size of windows of application(s)123 open on the remote desktop, which application(s) 123 are running onand/or displayed on the remote desktop of VM 120, and other information.

Transport agent plugin 126 interacts with transport client plugin 136for print redirection as described herein, such as via a virtual channelover network 146. In one embodiment, transport agent plugin 126 is aplugin installed in VM 120 ₁, such as within VDI agent 124, or is aseparate application from VDI agent 124. In one embodiment, transportagent plugin 126 communicates with a bridge component (not shown), whichin turn communicates with transport client plugin 136 on client device104.

According to an example, a request to perform a print job is initiatedon VM 120 ₁, such as by an application 123, directed to printing device140 of client device 104. Transport agent plugin 126 receives therequest, and determines whether data related to the print job needs tobe divided into slices before transmission to client device 104. In someembodiments, transport agent plugin 126 compares a size of the data(e.g., a PDU for the print job) to a size threshold. The size thresholdmay have been determined based on input from a user, such as viavirtualization manager 130 or another component that allows anadministrator to set parameters related to the remote computingenvironment. In one example, an administrator provided a transmissionrate limit for print jobs via interaction with a user interface, and thesize threshold is determined based on the transmission rate limit.

If the size of the data exceeds the threshold, transport agent plugin126 generates a plurality of slices based on the data, each slice beingless than or equal to the size threshold. The slices may be individualPDUs with PDU headers that allow the original data (e.g., a full PDU forthe print job) to be reconstructed from the plurality of slices. Forinstance, the PDU headers may include an identifier that is uniquelyassociated with the print job and an ordering value indicating whether agiven slice is the first slice, a middle slice, or the last slice of theprint job (or an ordering value that simply indicates the numericalorder of the slices and, in some embodiments, whether the slice is thelast slice). Transport agent plugin 126 may transmit the plurality ofslices over a series of consecutive time intervals, such as by sendingone slice per time interval, to transport client plugin 136 in order toachieve a transmission rate that is consistent with the transmissionrate limit for print jobs. Transport client plugin 136 may receive theslices, reconstruct the original data (e.g., the full PDU for the printjob), and pass the print job on to one or more additional components(e.g., an event handler for print jobs) for processing by printingdevice 140. Subsequently, printing device 140 may print the data.

It is noted that while transport agent plugin 126 is depicted separatelyfrom VDI agent 124, transport agent plugin 126 may alternatively beincluded within VDI agent 124.

Hardware platform 106 of each host 105 includes components of acomputing device such as one or more processors (CPUs) 108, systemmemory 110, a network interface 112, storage system 114, a host busadapter (HBA) 115, and other I/O devices such as, for example, a mouseand keyboard (not shown). CPU 108 is configured to execute instructions,for example, executable instructions that perform one or more operationsdescribed herein and that may be stored in memory 110 and in storage114. Network interface 112 enables host 105 to communicate with otherdevices via a communication medium, such as network 118 or network 128.Network interface 112 may include one or more network adapters, alsoreferred to as Network Interface Cards (NICs). Storage system 114represents persistent storage devices (e.g., one or more hard disks,flash memory modules, solid state disks, and/or optical disks). Host busadapter (HBA) couples host 105 to one or more external storages (notshown), such as a storage area network (SAN). Other external storagesthat may be used include network-attached storage (NAS) and othernetwork data storage systems, which may be accessible via NIC 112.

System memory 110 is hardware allowing information, such as executableinstructions, configurations, and other data, to be stored andretrieved. Memory 110 is where programs and data are kept when CPU 108is actively using them. Memory 110 may be volatile memory ornon-volatile memory. Volatile or non-persistent memory is memory thatneeds constant power in order to prevent data from being erased.Volatile memory describes conventional memory, such as dynamic randomaccess memory (DRAM). Non-volatile memory is memory that is persistent(non-volatile). Non-volatile memory is memory that retains its dataafter having power cycled (turned off and then back on). Non-volatilememory is byte-addressable, random access non-volatile memory.

Virtualization manager 130 communicates with hosts 105 via a network,shown as a management network 128, and carries out administrative tasksfor data center 102 such as managing hosts 105, managing VMs 120 runningwithin each host 105, provisioning VMs, migrating VMs from one host toanother host, and load balancing between hosts 105. Virtualizationmanager 130 may be a computer program that resides and executes in acentral server in data center 102 or, alternatively, virtualizationmanager 130 may run as a virtual appliance (e.g., a VM) in one of hosts105. One example of a virtualization manager is the vCenter Server™product made available from VMware, Inc.

Gateway 138 provides VMs 120 and other components in data center 102with connectivity to network 146. Gateway 138 may manage external publicIP addresses for VMs 120, route traffic incoming to and outgoing fromdata center 102, and provide networking services, such as firewalls,network address translation (NAT), dynamic host configuration protocol(DHCP), and load balancing. Gateway 138 uses data network 118 totransmit data network packets to hosts 105. Gateway 138 may be a virtualcomputing instance, a physical device, or a software module runningwithin host 105. Gateway 138 may include two gateways: a managementgateway for management network 128 and a data gateway for data network118.

FIG. 2 is an illustration 200 of a prior art technique for printredirection in a remote computing environment. Illustration 200 includesan agent side 210, which may be representative of a remote device suchas a host 105 or VM 120 of FIG. 1 , and a client side 220, which may berepresentative of a client device similar to client device 104 of FIG. 1.

In illustration 200, a PDU 212 for a print job is sent via transmission260 from agent side 210 to client side 220. PDU 212 may be generatedbased on a request from an application on agent side 210 to print datafrom agent side 210 on a printer associated with client side 220. PDU212 includes a header indicting a type 214 and size 216 of the PDU and apayload 218 that includes data to be printed. Type 214 may indicate thatthe PDU is for a print job, as opposed to PDUs for different types offeatures, such as for I/O operations. Size 216 indicates a size of theprint job, such as an amount of data to be printed (e.g., a size ofpayload 218).

By transmitting PDU 212 in its entirety from agent side 210 to clientside 220 (e.g., in a single transmission or at least at a hightransmission rate), the prior art technique depicted in illustration 200may result in undue network congestion. Print jobs generally have alower priority than other types of data transmissions, such as userinput redirection, and are generally not time-sensitive. A user does notexpect a print job to begin immediately upon request, and printersgenerally take a certain amount of time to process the job and beginprinting. Thus, causing network congestion by rapidly transmitting PDU212 from agent side 210 to client side 220 is unnecessary and maypotentially interfere with the functioning of higher-priorityfunctionality.

As such, embodiments of the present disclosure involve rate limitingprint redirection, as described in more detail below with respect toFIG. 3 .

FIG. 3 is an illustration 300 of an improved technique for printredirection in a remote computing environment, according to embodimentsof the present disclosure. The issues described above with respect toFIG. 2 are addressed by techniques described herein, such as withrespect to FIG. 3 .

Illustration 300 includes agent side 210, client side 220, and PDU 212of FIG. 2 . However, rather than redirecting a print job in a singletransmission and/or at a high transmission rate, as in FIG. 2 ,illustration 300 depicts redirecting print jobs via a plurality ofsmaller slices that are sent in separate time intervals in order toimplement a transmission rate limit.

On agent side 210, PDU 212 is divided at step 370 into a plurality ofsmaller PDUs 312, 314, 316, and 318, which are examples of slices ordata slices. For instance, payload 218 may be compared to a sizethreshold and, upon determining that payload 218 exceeds the sizethreshold, payload 218 may be broken into smaller payloads 352, 354,356, and 358. Payloads 352, 354, and 356 may all be equal to the sizethreshold while payload 358 may be smaller than the size threshold. Forexample, if payload 218 is 1500 KB (1.5 MB) and the size threshold is400 KB (e.g., based on a transmission rate limit of 400 KB per second),then payloads 352, 354, and 356 may each be 400 KB, while payload 358may be 300 KB (e.g., because only 300 KB remain in the 1500 KB payload218 after the other three 400 KB slices). In some embodiments, payloads352, 354, 356, and 358 may have the same or different sizes all lessthan or equal to the threshold.

In addition to the type 214 and size 216 from PDU 212, the header ofeach of PDUs 312, 314, 316, and 318 further includes an ID 322 and anordering value 324, 326, 327, or 328. ID 322 is an identifier that isunique to the print job and is common to all of PDUs 312, 314, 316, and318. Ordering values 324, 326, 327, and 328 each indicate whether agiven PDU is a first slice, middle slice, or last slice. For instance,ordering value 324 indicates that PDU 312 is a first slice, orderingvalues 326 and 327 indicate that PDUs 314 and 316 are middle slices, andordering value 328 indicates that PDU 318 is a last slice.

PDUs 312, 314, 316, and 318 are transmitted from agent side 210 toclient side 220 as transmissions 360, 362, 364, and 366, each of whichis sent in a separate time interval. For example, the time interval maybe one second, and PDUs 312, 314, 316, and 318 may be sent in a seriesof consecutive one second intervals in order to comply with atransmission rate limit of 400 KB per second.

PDUs for other print jobs, as well as other types of data, may betransmitted in the same time intervals as transmissions 360, 362, 364,and 366. Thus, the PDU headers may be needed to determine which printjob each PDU belongs to and to determine an order in which the PDUsshould be used to reconstruct a print job.

On client side 220, at step 380, PDU 212 is reconstructed from PDUs 312,314, 316, and 318. In an example, when a transport client plugin onclient side 220 receives PDU 312, it determines based on ordering value324 that PDU 312 is the first slice for ID 322. As such, the transportclient plugin creates a new buffer for ID 322 and places PDU 312 in thebuffer. Next, upon receiving PDUs 314 and 316, the transport clientplugin determines based on ordering values 326 and 327 that PDUs 314 and316 are middle slices for ID 322. Accordingly, the transport clientplugin adds PDUs 314 and 316, in the order they are received, to thebuffer for ID 322. Finally, upon receiving PDU 318, the transport clientplugin determines based on ordering value 328 that PDU 318 is the lastslice for ID 322. As such, the transport client plugin adds PDU 318 tothe end of the buffer for ID 322. In alternative embodiments, orderingvalues 324, 326, 327, and 328 are sequential numerical values (e.g., 0,1, 2, 3), and PDUs 312, 314, 316, and 318 are added to the buffer in theorder of the numerical values. In some embodiments, ordering value 328may indicate that PDU 318 is the last slice (e.g., by the use of aparticular value and/or a separate indicator).

The transport client plugin then reconstructs PDU 212 based on thebuffer for ID 322. For example, the transport client plugin mayreconstruct payload 218 by combining payloads 352, 354, 356, and 358 inthe order in which the PDUs were added to the buffer, and mayreconstruct the header of PDU 212 based on the type 214 and size 216included in all of PDUs 312, 314, 316, and 318.

Subsequently, PDU 212 may be further processed, such as by an eventhandler, on client side 220 and the print job is printed by the printeron client side 220.

FIG. 4 illustrates example operations 400 related to print redirectionin a remote computing environment. For example, operations 400 may beperformed by one or more components of client device 104 and/or host 105of FIG. 1 .

Operations 400 begin at step 402, with receiving, on a remote devicethat is remote from a client device, a request to perform a printingtask using a printing device associated with the client device.

Operations 400 continue at step 404, with determining, on the remotedevice, that data associated with the request to perform the printingtask exceeds a size threshold. In some embodiments, the size thresholdis determined based on input received via a user interface, such asdefining a transmission rate limit for print redirections.

Operations 400 continue at step 406, with generating, on the remotedevice, a plurality of data slices based on the data, wherein eachrespective data slice of the plurality of data slices comprises arespective subset of the data that does not exceed the size threshold.The plurality of data slices may, for example, comprise a plurality ofprotocol data units (PDUs) (e.g., generated by the VDI agent or acomponent associated with the VDI agent).

Operations 400 continue at step 408, with transmitting, from the remotedevice to the client device, the plurality of data slices as separatetransmissions in separate time intervals along with information thatallows the data to be reconstructed from the plurality of data slicesfor performing the printing task on the client device.

In some embodiments, the information that allows the data to bereconstructed from the plurality of data slices for printing on theclient device comprises ordering values indicating an order of theplurality of slices (e.g., sequential numerical values or, for eachrespective data slice of the plurality of data slices, a valueindicating whether the respective data slice is a first data slice, amiddle data slice, or a last data slice), and an identifier that iscommon to the plurality of data slices.

In some cases, the remote device comprises a virtual desktopinfrastructure (VDI) agent, the client device comprises a VDI client(e.g., that accesses a virtual desktop via the VDI agent), and therequest to perform the printing task is generated by a virtual desktopassociated with the VDI agent.

In certain embodiments, the plurality of data slices are transmittedfrom the remote device to the client device via a virtual channel. Insome cases, a length of each of the separate time intervals isdetermined based on a size of a respective data slice of the pluralityof data slices. For example, according to certain embodiments of thepresent disclosure, only one of the plurality of data slices may betransmitted during each respective time interval of the separate timeintervals.

It should be understood that, for any process described herein, theremay be additional or fewer steps performed in similar or alternativeorders, or in parallel, within the scope of the various embodiments,consistent with the teachings herein, unless otherwise stated.

The various embodiments described herein may employ variouscomputer-implemented operations involving data stored in computersystems. For example, these operations may require physical manipulationof physical quantities—usually, though not necessarily, these quantitiesmay take the form of electrical or magnetic signals, where they orrepresentations of them are capable of being stored, transferred,combined, compared, or otherwise manipulated. Further, suchmanipulations are often referred to in terms, such as producing,identifying, determining, or comparing. Any operations described hereinthat form part of one or more embodiments according to the presentdisclosure may be useful machine operations. In addition, one or moreembodiments according to the present disclosure also relate to a deviceor an apparatus for performing these operations. The apparatus may bespecially constructed for specific required purposes, or it may be ageneral purpose computer selectively activated or configured by acomputer program stored in the computer. In particular, various generalpurpose machines may be used with computer programs written inaccordance with the teachings herein, or it may be more convenient toconstruct a more specialized apparatus to perform the requiredoperations.

The various embodiments described herein may be practiced with othercomputer system configurations including hand-held devices,microprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.

One or more embodiments according to the present disclosure may beimplemented as one or more computer programs or as one or more computerprogram modules embodied in one or more computer readable media. Theterm computer readable medium refers to any data storage device that canstore data which can thereafter be input to a computer system—computerreadable media may be based on any existing or subsequently developedtechnology for embodying computer programs in a manner that enables themto be read by a computer. Examples of a computer readable medium includea hard drive, network attached storage (NAS), read-only memory,random-access memory (e.g., a flash memory device), a CD (CompactDiscs)-CD-ROM, a CD-R, or a CD-RW, a DVD (Digital Versatile Disc), amagnetic tape, and other optical and non-optical data storage devices.—The computer readable medium can also be distributed over a networkcoupled computer system so that the computer readable code is stored andexecuted in a distributed fashion.

Although one or more embodiments according to the present disclosurehave been described in some detail for clarity of understanding, it willbe apparent that certain changes and modifications may be made withinthe scope of the claims. Accordingly, the described embodiments are tobe considered as illustrative and not restrictive, and the scope of theclaims is not to be limited to details given herein, but may be modifiedwithin the scope and equivalents of the claims. In the claims, elementsand/or steps do not imply any particular order of operation, unlessexplicitly stated in the claims.

Virtualization systems in accordance with the various embodiments may beimplemented as hosted embodiments, non-hosted embodiments or asembodiments that tend to blur distinctions between the two, are allenvisioned. Furthermore, various virtualization operations may be whollyor partially implemented in hardware. For example, a hardwareimplementation may employ a look-up table for modification of storageaccess requests to secure non-disk data.

Certain embodiments as described above involve a hardware abstractionlayer on top of a host computer. The hardware abstraction layer allowsmultiple contexts to share the hardware resource. In one embodiment,these contexts are isolated from each other, each having at least a userapplication running therein. The hardware abstraction layer thusprovides benefits of resource isolation and allocation among thecontexts. In the foregoing embodiments, virtual machines are used as anexample for the contexts and hypervisors as an example for the hardwareabstraction layer. As described above, each virtual machine includes aguest operating system in which at least one application runs. It shouldbe noted that these embodiments may also apply to other examples ofcontexts, such as containers not including a guest operating system,referred to herein as “OS-less containers” (see, e.g., www.docker.com).OS-less containers implement operating system-level virtualization,wherein an abstraction layer is provided on top of the kernel of anoperating system on a host computer. The abstraction layer supportsmultiple OS-less containers, each including an application and itsdependencies. Each OS-less container runs as an isolated process in userspace on the host operating system and shares the kernel with othercontainers. The OS-less container relies on the kernel's functionalityto make use of resource isolation (CPU, memory, block I/O, network,etc.) and separate namespaces and to completely isolate theapplication's view of the operating environments. By using OS-lesscontainers, resources can be isolated, services restricted, andprocesses provisioned to have a private view of the operating systemwith their own process ID space, file system structure, and networkinterfaces. Multiple containers can share the same kernel, but eachcontainer can be constrained to only use a defined amount of resourcessuch as CPU, memory and I/O. The term “virtualized computing instance”as used herein is meant to encompass both VMs and OS-less containers.

Many variations, modifications, additions, and improvements arepossible, regardless of the degree of virtualization. The virtualizationsoftware can therefore include components of a host, console, or guestoperating system that performs virtualization functions. Pluralinstances may be provided for components, operations or structuresdescribed herein as a single instance. Boundaries between variouscomponents, operations and data stores are somewhat arbitrary, andparticular operations are illustrated in the context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within the scope of the invention(s). Ingeneral, structures and functionality presented as separate componentsin exemplary configurations may be implemented as a combined structureor component. Similarly, structures and functionality presented as asingle component may be implemented as separate components. These andother variations, modifications, additions, and improvements may fallwithin the scope of the appended claim(s).

1. A method of print redirection in a remote computing environment, themethod comprising: receiving, on a remote device that is remote from aclient device, a request to perform a printing task using a printingdevice associated with the client device; determining, on the remotedevice, that data associated with the request to perform the printingtask exceeds a size threshold, wherein the size threshold is determinedbased on a configured transmission rate limit for printing tasks;generating, on the remote device, a plurality of data slices based onthe data, wherein each respective data slice of the plurality of dataslices comprises a respective subset of the data that does not exceedthe size threshold; and transmitting, from the remote device to theclient device, the plurality of data slices as separate transmissions inseparate consecutive time intervals along with information that allowsthe data to be reconstructed from the plurality of data slices forperforming the printing task on the client device, wherein each of theseparate consecutive time intervals has a length that is based on theconfigured transmission rate limit for printing tasks.
 2. The method ofclaim 1, wherein the information that allows the data to bereconstructed from the plurality of data slices for printing on theclient device comprises: ordering values indicating an order of theplurality of slices; and an identifier that is common to the pluralityof data slices.
 3. The method of claim 1, further comprising determiningthe size threshold based on input received via a user interface.
 4. Themethod of claim 1, wherein: the remote device comprises a virtualdesktop infrastructure (VDI) agent; the client device comprises a VDIclient; and the request to perform the printing task is generated by avirtual desktop associated with the VDI agent.
 5. The method of claim 4,wherein the plurality of data slices comprise a plurality of protocoldata units (PDUs) generated by the VDI agent or a component associatedwith the VDI agent, and wherein the plurality of data slices aretransmitted from the remote device to the client device via a virtualchannel.
 6. The method of claim 1, wherein the length of each of theseparate consecutive time intervals is determined based further on asize of a respective data slice of the plurality of data slices.
 7. Themethod of claim 1, wherein only one of the plurality of data slices istransmitted during each respective time interval of the separateconsecutive time intervals.
 8. A system for print redirection in aremote computing environment, the system comprising: at least onememory; and at least one processor coupled to the at least one memory,the at least one processor and the at least one memory configured to:receive, on a remote device that is remote from a client device, arequest to perform a printing task using a printing device associatedwith the client device; determine, on the remote device, that dataassociated with the request to perform the printing task exceeds a sizethreshold, wherein the size threshold is determined based on aconfigured transmission rate limit for printing tasks; generate, on theremote device, a plurality of data slices based on the data, whereineach respective data slice of the plurality of data slices comprises arespective subset of the data that does not exceed the size threshold;and transmit, from the remote device to the client device, the pluralityof data slices as separate transmissions in separate consecutive timeintervals along with information that allows the data to bereconstructed from the plurality of data slices for performing theprinting task on the client device, wherein each of the separateconsecutive time intervals has a length that is based on the configuredtransmission rate limit for printing tasks.
 9. The system of claim 8,wherein the information that allows the data to be reconstructed fromthe plurality of data slices for printing on the client devicecomprises: ordering values indicating an order of the plurality ofslices; and an identifier that is common to the plurality of dataslices.
 10. The system of claim 8, wherein the at least one processorand the at least one memory are further configured to determine the sizethreshold based on input received via a user interface.
 11. The systemof claim 8, wherein: the remote device comprises a virtual desktopinfrastructure (VDI) agent; the client device comprises a VDI client;and the request to perform the printing task is generated by a virtualdesktop associated with the VDI agent.
 12. The system of claim 11,wherein the plurality of data slices comprise a plurality of protocoldata units (PDUs) generated by the VDI agent or a component associatedwith the VDI agent, and wherein the plurality of data slices aretransmitted from the remote device to the client device via a virtualchannel.
 13. The system of claim 8, wherein the length of each of theseparate consecutive time intervals is determined based further on asize of a respective data slice of the plurality of data slices.
 14. Thesystem of claim 8, wherein only one of the plurality of data slices istransmitted during each respective time interval of the separateconsecutive time intervals.
 15. A non-transitory computer-readablemedium storing instructions that, when executed by one or moreprocessors, cause the one or more processors to: receive, on a remotedevice that is remote from a client device, a request to perform aprinting task using a printing device associated with the client device;determine, on the remote device, that data associated with the requestto perform the printing task exceeds a size threshold, wherein the sizethreshold is determined based on a configured transmission rate limitfor printing tasks; generate, on the remote device, a plurality of dataslices based on the data, wherein each respective data slice of theplurality of data slices comprises a respective subset of the data thatdoes not exceed the size threshold; and transmit, from the remote deviceto the client device, the plurality of data slices as separatetransmissions in separate consecutive time intervals along withinformation that allows the data to be reconstructed from the pluralityof data slices for performing the printing task on the client device,wherein each of the separate consecutive time intervals has a lengththat is based on the configured transmission rate limit for printingtasks.
 16. The non-transitory computer-readable medium of claim 15,wherein the information that allows the data to be reconstructed fromthe plurality of data slices for printing on the client devicecomprises: ordering values indicating an order of the plurality ofslices; and an identifier that is common to the plurality of dataslices.
 17. The non-transitory computer-readable medium of claim 15,wherein the instructions, when executed by the one or more processors,further cause the one or more processors to determine the size thresholdbased on input received via a user interface.
 18. The non-transitorycomputer-readable medium of claim 15, wherein: the remote devicecomprises a virtual desktop infrastructure (VDI) agent; the clientdevice comprises a VDI client; and the request to perform the printingtask is generated by a virtual desktop associated with the VDI agent.19. The non-transitory computer-readable medium of claim 18, wherein theplurality of data slices comprise a plurality of protocol data units(PDUs) generated by the VDI agent or a component associated with the VDIagent, and wherein the plurality of data slices are transmitted from theremote device to the client device via a virtual channel.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the lengthof each of the separate consecutive time intervals is determined basedfurther on a size of a respective data slice of the plurality of dataslices.